\documentclass[a4paper]{article}
\begin{document}


\section{Tasks}
\begin{itemize}
\item Review
\item Mapping problem analysis to testing - Fred and Niv
\item Success criteria - separate section
\item Testing priorities
\item Define testing details
\item Implementation section and code - Tomasz
\end{itemize}

\section{Testing}

Correctness:
\begin{itemize}
\item Message Flow / Protocol
\item Structural correctness (unit testing)
\item Search
\item Buffers (all messages are executed)
\item Static replication
\end{itemize}


Performance measurements:
\begin{itemize}
\item How many messages ?
\item Storage size
\item Enabled / Disabled expansion-retraction
\item Network listener: Bandwitdth (messages/bandwidth per node)
\item Storage Distribution  (messages/bandwidth load) ; Permanent / Volatile Memory load
\item Time to search Results:
\item * with index expansion
\item * without index expansion
\item Dynamic thresholds (Assumptions: TBD)
\item Maintenance procedure - how often do they go ?
\item Dynamic Replication
\end{itemize}


Benchmarks:
\begin{itemize}
\item Look at delicious to get ideas about data
\end{itemize}


\section{Success criteria}
\begin{itemize}
\item Behavior correctness
\item Data integrity
\item Scalability: Load is evenly distributed or at least in a manner that the system performs well.
\item Performance
\item Fairness (usability)
\item Self-maintenance
\end{itemize}

\section{Questions to Arne}
\begin{itemize}
\item Self vs. increasing leafset.
\end{itemize}

\section{Test cases}

\subsection{tagging Test}
\begin{itemize}
\item add data
\item check if exists
\end{itemize}

\subsection{untagging test}
\begin{itemize}
\item add data more than once to inc rank
\item remove once
\item search -> result decremented rank
\item remove again
\item search -> not exists anymore (including leaf-set) - due that reason possibly 'search' after sync.
\end{itemize}

\subsection{Testing search}
\begin{itemize}
\item add data with different ranks
\item make sure you get complete result set ; sorted
\end{itemize}

\subsection{Load testing}
\begin{itemize}
\item Use the min,med,big.txt files to supply system with data
\item for each load data measure: load distribution, number of bytes by each msgs sent,
response time for basic and complex queries
\end{itemize}

\subsection{Stress testing}
\begin{itemize}
\item Try to find a boundary value which will define max data load our system can handle
by generating many nodes ; lots of data and comparing results
\end{itemize}

\subsection{Distribution test}
\begin{itemize}
\item Prepare data so that you can observe proper distribution and at the same time
buffering of messages. Result: proper output with no UPDATE msgs while distribution.
\end{itemize}

\subsection{Retraction test}
\begin{itemize}
\item Very similiar to distribution test.
\end{itemize}

\subsection{Leaf set replication test}
\begin{itemize}
\item Add data
\item Wait to synchronize
\item Kill node
\item Search - make sure you still have the same result set.
\end{itemize}

\end{document}
